Enclosure for surveillance hardware

ABSTRACT

The enclosure for surveillance hardware provided herein protects the hardware from external elements and from damage. The enclosure may be configured for a node of a peer to peer surveillance architecture. The enclosure may comprise a sealed component chamber and an adjacent support chamber. The sealed component chamber may enclose the components therein in an air or watertight manner. The support chamber may comprise an airflow system and thermal conductor which regulates the temperature in the component chamber. The enclosure may be formed from a multilayer material having various protective qualities. A controller may be provided to control operation of the airflow system and thermal conductor in response to changes in temperature.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation-in-part of U.S. patent applicationSer. No. 12/154,477 entitled Peer to Peer Surveillance Architecture,filed May 23, 2008.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to surveillance system hardware, particularly toan enclosure for protecting and supporting surveillance devices. Theinvention also relates to enclosures for surveillance nodes used in peerto peer surveillance architectures.

2. Related Art

Surveillance is widely utilized in modern society. Governments,corporations, groups, and even individuals use surveillance to promotepublic safety and to deter and prevent crime as well as for generalmonitoring.

Traditional surveillance systems generally provide audio and videomonitoring through an interconnected hierarchical system. For example, aclosed-circuit television (CCTV) system may provide video monitoringthrough a set of closed-circuit cameras connected to a single standalone aggregation device where the video feeds from the cameras aresent. The captured information may then be viewed through theaggregation device such as on one or more video screens.

To function properly, a CCTV or other similar traditional systemrequires a central controller or device which accepts signals fromcameras and which may also provide control instructions to the devices.This allows every camera to be monitored and controlled from a singlelocation. However, this introduces a single point of failure in that thefailure of the central controller would render the entire surveillancesystem inoperative. Thus, such systems are said to be fragile as afailure of the central controller or the connections between thecontroller and the cameras either impairs or completely prevents thesurveillance system from functioning. This fragility is highlyundesirable in a surveillance system especially where public safety isconcerned.

With the introduction of digital and networked devices, surveillancecameras could be connected via standard wired or wireless networkconnections. This was an improvement in that one or more standardnetwork connections could be used by capture devices rather than aspecialized, dedicated, or proprietary video connection. In addition,digital video may be sent across vast distances through digitalnetworks, such as the Internet, which was not possible without greatexpense using traditional CCTV systems.

However, network based surveillance systems continue to rely on acentralized controller to function. The video or other surveillanceinformation is still aggregated at the centralized controller whichfacilitates observation and analysis of the information gathered. Thus,the single point of failure has remained through the transition fromtraditional CCTV and similar systems to network based surveillancesystems.

It is true that these traditional systems may be configured to havebackup central controllers. While these backup systems provide increasedreliability they do so at increased cost and often do not provide aseamless transition from the failed equipment to its associated backupdevice. In surveillance, any downtime including downtime associated withswitching to a backup device is highly undesirable.

Traditional systems are also difficult to update for new circumstancesor environments. For example, moving one or more cameras to a newlocation or including additional cameras or other collection devicesrequires installation of at least one connection from each camera orcollection device to the central controller. These connections are oftenphysical connections, such as network or coaxial cabling, which aredifficult to install especially in existing structures.

Traditional surveillance devices are also vulnerable to the elementssuch as excessive temperatures and physical damage. In addition, thesedevices generally are limited to specific operating environments. Thus,what is desired and disclosed herein is an enclosure for a peer to peersurveillance architecture that encloses and protects surveillancedevices while expanding their possible operating environments.

SUMMARY OF THE INVENTION

An enclosure for a node of a peer to peer surveillance architecture isdescribed herein. In general, the enclosure protects the components of anode from external elements and damage. The enclosure may regulate theenvironment surrounding a node's components and may be configured withredundant parts to provide reliable operation.

In one embodiment, the enclosure comprises a rigid multilayer material,a sealed component chamber formed from the multilayer material andconfigured to enclose one or more components of the node, and a supportchamber adjacent to the sealed component chamber. It is noted that thesealed component chamber may include a dome configured to allow a camerato capture images through it in some embodiments. In addition, themultilayer material may comprise various layers. For example, themultilayer material may comprise an aluminum layer, an insulating layer,and a coating layer.

The support chamber may comprise one or more vents configured to allowthe passage of air, a thermal conductor configured to lower thetemperature of the sealed component chamber, an airflow systemconfigured to ensure no degenerative airflow, and a power supply. Also,the support chamber may comprise one or more baffles to direct the atleast one airflow.

The parts of a support chamber may be configured in various ways. Toillustrate, the airflow system may comprise a fan assembly having atleast two fans aligned by at least one spacer. Spacing of fans mustensure no degradation of backpressure. The airflow system may be sealedto ensure sufficient airflow. In addition, the thermal conductor may bea Peltier device comprising a cooled portion and a heated portionwhereby the cooled portion is in physical contact with the sealedcomponent chamber and the heated portion is cooled by the airflowsystem. At least a portion of the cooled portion may be within thesealed component chamber in some embodiments.

The enclosure may also comprise one or more heating elements, and acontroller configured to activate the one or more heating elements toprevent damage to the components from cold temperatures.

In one embodiment, the enclosure for a node may comprise a sealedcomponent chamber configured to enclose one or more components of thenode, and a support chamber adjacent the sealed component chamber. Thesupport chamber may comprise an air inflow vent at a first end of thesupport chamber, an air outflow vent at a second end of the supportchamber, an airflow system adjacent the air inflow vent configured togenerate at least one airflow, and a thermal conductor adjacent theairflow system. A portion of the thermal conductor may be in contactwith the sealed component chamber.

The airflow system may be configured in various ways. For example, theairflow system may be sealed to the support chamber by one or moremounts. In addition, the airflow system may comprise at least two fansaligned by at least one spacer.

The support chamber may comprise a power supply adjacent the thermalconductor, a baffle adjacent the air outflow vent, or both. Also, insome embodiments, the support chamber may further comprise a controllerconfigured to monitor key criteria of the node. The controller maycontrol the airflow system to ensure safe operation of equipment withinthe node. The controller may also provide status to monitoring equipmentexternal to the node.

A method of protecting components of a node within an enclosure is alsoprovided herein. In one embodiment, the method comprises providing asealed component chamber comprising a multilayer material to enclose oneor more components of a node, providing electrical power to one or morecomponents with a power supply, transferring the heat from the sealedcomponent chamber to an adjacent support chamber through a thermalconductor, generating at least one airflow with a airflow system withinthe support chamber to cool the thermal conductor, measuring at leastone temperature of the sealed component chamber, increasing power to thethermal conductor if the at least one temperature increases, anddisabling the electrical power to the one or more components if the atleast one temperature increases beyond a heat threshold for the one ormore components. In some embodiments, one or more heating elements maybe activated if the at least one temperature is below a cold thresholdfor the one or more components. Also, one or more error conditions ofthe airflow system via a transceiver may be reported. It is contemplatedthat the at least one airflow may be generated with a fan assemblywithin the support chamber according to the method.

Other systems, methods, features and advantages of the invention will beor will become apparent to one with skill in the art upon examination ofthe following figures and detailed description. It is intended that allsuch additional systems, methods, features and advantages be includedwithin this description, be within the scope of the invention, and beprotected by the accompanying claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The components in the figures are not necessarily to scale, emphasisinstead being placed upon illustrating the principles of the invention.In the figures, like reference numerals designate corresponding partsthroughout the different views.

FIG. 1 illustrates an example embodiment of the peer to peersurveillance architecture as it may be deployed.

FIG. 2A is a block diagram illustrating an example embodiment of thepeer to peer surveillance architecture where each node is connectedthrough a network.

FIG. 2B is a block diagram illustrating an example embodiment of thepeer to peer surveillance architecture where each node is connectedthrough more than one independent network.

FIG. 3 is a block diagram illustrating an example embodiment of a node.

FIG. 4 is a block diagram illustrating an example embodiment of acapture node.

FIG. 5 is a block diagram illustrating an example embodiment of aviewing node.

FIG. 6 is a block diagram illustrating an example embodiment of acontent storage node.

FIG. 7 is a block diagram illustrating an example embodiment of a servernode.

FIG. 8A is a front perspective view of an example embodiment of anenclosure.

FIG. 8B is a perspective view of an example embodiment of the multilayermaterial of an enclosure.

FIG. 8C is a rear perspective view of an example embodiment of anenclosure.

FIG. 8D is a cross section view of an example embodiment of anenclosure.

FIG. 9 is a side interior view of an example embodiment of an enclosure.

FIG. 10 is a block diagram illustrating an example embodiment of acontrol system.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following description, numerous specific details are set forth inorder to provide a more thorough description of the present invention.It will be apparent, however, to one skilled in the art, that thepresent invention may be practiced without these specific details. Inother instances, well-known features have not been described in detailso as not to obscure the invention.

Generally, the peer to peer surveillance architecture comprises one ormore nodes configured to capture, analyze, store, and presentsurveillance information. As discussed further below, surveillanceinformation comprises a wide variety of information including video andaudio. As used herein, peer to peer means that each node within thesurveillance architecture operates such that it is not dependent on(i.e. does not rely on) its peer nodes. This allows the surveillancearchitecture to have no single point of failure making it extremelyrobust. The failure of or damage to individual nodes, components, orcommunication links cannot cause the system to function at less thanfull capacity when a peer to peer or non-dependent relationship existsbetween each node and its peers.

The surveillance architecture may be configured to balance requirementsand capability. For example, the architecture may be configured for ahigh or complete redundancy, but may also be configured according toparticular requirements based on the necessary functionality,redundancy, and budget considerations.

As will be described further below, the peer to peer surveillancearchitecture generally comprises one or more capture nodes, servernodes, content storage nodes, and viewing nodes. The capture nodesgenerally record or capture surveillance information and may beconfigured to capture specific types of information, such as a cameranode which captures video surveillance information. The capturedinformation may be viewed, stored, or analyzed by the other nodes,including other capture nodes. The architecture is able to providecomplete redundancy through these nodes, which are configured tofunction without depending on any other node or any single communicationlink.

The peer to peer surveillance architecture combines this redundancy withhigh adaptability and easy deployment, both of which are among theadvantages over traditional surveillance systems. This allows collectionof surveillance information from a wide range of target areas and isgenerally made possible through various wireless, cellular, and othernetwork technologies, and allows for stationary and mobile surveillancesystems that may be rapidly deployed virtually anywhere as desired. Forexample, the architecture allows capture nodes to be mounted onbuildings, utility poles, in jails, in parks, throughout downtown areas,and intersections even where there are no physical communication linkssuch as network or other cables.

The advantages of the peer to peer surveillance architecture'sreliability and adaptability can be readily seen with regard to publicsafety. Surveillance enhances public safety and security by allowingpolice and other security agencies or organizations to monitor citizensafety, specific events, congestion, and even fight graffiti. Inaddition, surveillance serves as a force multiplier, allowing forexample, police or municipalities to expand their coverage withoutadditional officers. Thus, the architecture's reliability ensuresreliable surveillance for these purposes, and its adaptability allowsrapid deployment to monitor special events, such as but not limited tosporting events or conventions as well as the ability to quickly andeasily remove surveillance once the event is over.

The peer to peer surveillance architecture may also provide analysis ofsurveillance information. This greatly expands surveillance capabilitieswithout the need for increased personnel as well. For example, thearchitecture may provide automated license plate recognition, theftdetection, and traffic congestion monitoring. The architecture mayprovide notifications to users or to nodes within the architecture whencertain events are present or detected in the surveillance information.

The peer to peer surveillance architecture will now be described withregard to FIGS. 1-7. FIG. 1 illustrates an exemplary embodiment of thesurveillance architecture deployed in an urban setting. In oneembodiment, the surveillance architecture comprises one or more nodes100 communicating through a network 104 via one or more communicationlinks 108.

The network 104 allows communication between one or more nodes 100 tooccur and may be any type of communication network or path now know orlater developed. The network 104 may comprise various communicationlinks 108 including wired and wireless links and utilize variouscommunication protocols. In one embodiment, the network 104 is a packetswitched network such as an Internet Protocol (IP) network. Any packetbased communication protocol, known or later developed, may be used.This includes connection based protocols such as Transmission ControlProtocol (TCP), frame relay, and Asynchronous Transfer Mode (ATM). Thisalso includes connectionless protocols such as User Datagram Protocol(UDP). It is contemplated that the network 104, or a portion of it, mayalso be a circuit switched network in one or more embodiments and thatcommunications between nodes may be encrypted, such as through one ormore Virtual Private Networking (VPN) connections to securecommunications across the network.

Each node 100 communicates through the network 104 via one or morecommunication links 108. The communication links 108 may each representone or more independent communication links to a network 104 thusallowing each node 100 to have redundant communication links 108. Thecommunication links 108 may be any communication link capable ofcarrying data now know or later developed. For example, thecommunication link 108 may comprise electrical, optical, or other cable.The communication link 108 may utilize physical layer topologies such asbut not limited to Category 5 or 6, SM or MM fiber, DSL and Long RangeEthernet. The communication link 108 may also be a wirelesscommunication link such as a cellular or other wireless link. Wirelesscommunication links 108 may utilize physical layer topologies such asbut not limited to 802.11a/b/g, WiMAX EVDO, GPRS, Long Range Ethernet,and DSL as well as any other wireless protocol capable of carrying datanow know or later developed. It is contemplated that these wirelessconnections or networks may operate across on one or more frequenciescapable of supporting data communication such as cellular frequencies,the 4.9 GHz public safety frequency, licensed and unlicensed wireless(e.g. 70 GHz and 90 GHz), 2.4 GHz, and 5.8 GHz, and other microwave andsatellite communication frequencies among others. Wireless connectionsmay also comprise optical wireless connections, such as a laser or otherlight based communication. It is noted that, as described regarding thenetwork 104, any communication protocol now know or later developedwhether packet switched, circuit switched, connection based,connectionless, or otherwise may be used to facilitate communication viathe communication link 108.

FIG. 2A is a block diagram illustrating an embodiment of the peer topeer surveillance architecture where each node is connected through onenetwork, similar to the above. FIG. 2B is a block diagram illustratingan embodiment of the surveillance architecture where each node 100 isconnected through more than one independent network 104. In addition,the networks 104 themselves may be connected by a communication link 108as well. Thus, communications to and from each node 100 may be routedthrough a single network or both networks. The communication links 108from each node 100 to each network 104 provide redundancy allowing thesurveillance architecture to fully function even if one or more of thecommunication links 108 are not operational. In addition, as statedabove, each communication link 108 may comprise one or more independentconnections, as desired, further increasing the architecture'sreliability.

Of course, a network 104 or networks may be configured in a multitude ofways as is well known in the art. In one or more embodiments, thenetwork 104 may be a single switch or router such as in a local areanetwork, or may include one or more switches, routers, and otherdevices, such as a wide area network or the Internet. It is noted thatnodes 100 may also communicate directly through one another rather thanthrough one or more other devices. For example, two nodes 100 may have adirect wireless connection between one another such as an ad hoc802.11a/b/g connection or a direct cable connection. It is contemplatedthat the nodes 100 may communicate with a network through another nodein one or more embodiments.

In one or more embodiments, each node 100 may be connected to everyother node through a logical connection, such as for example, nodesconnected to one another in an IP or other packet switched network.Generally, a logical connection may be thought of as the end to endconnection which allows data from a source to reach its properdestination as it travels across one or more physical or wirelessconnections. The term virtual matrix switch as used herein refers to thelogical connections that allow communication between the nodes 100 of asurveillance system.

The virtual matrix switch allows surveillance information to becommunicated between individual nodes 100, but also supportsmulticasting surveillance information to a plurality or all of the nodesregardless of the underlying physical or wireless connection type. Whenconnected through a virtual matrix switch, each node 100 will be in avirtual or logical network with only its peer nodes in one or moreembodiments. To illustrate, in one embodiment, each node 100 isconnected to peer nodes by one or more networks and communication links.Though these networks and communication links may be public or privatenetworks and communication links shared by other devices, the virtualmatrix switch provides a virtual or logical network which only the nodes100 are part of. Communications within the virtual matrix switch may beencrypted, such as through GRE tunneling or VPN connections, in someembodiments.

FIG. 3 illustrates an embodiment of a node 100. In one or moreembodiments, a node 100 may comprise any combination of one or moreprocessors 304, memory 308, and storage 312 that is capable ofprocessing, and executing machine readable code from the memory 308,storage 312, or both in one or more embodiments. Generally, theprocessor 304 may be any device capable of executing machine readablecode and transmitting and receiving data. The memory 308 and serverstorage 312 may be any data storage device or devices capable of storingdata. The memory 308 and storage 312 will typically allow both readingand writing data, however, in some embodiments at least a portion or allof either the memory 308 or storage 312 may be read only. It is notedthat in some embodiments, memory 308 or storage 312 alone will besufficient to store any data or machine readable code required by thenode 100 and that because of this, not all embodiments will require bothmemory 308 and storage 312.

In some embodiments, the machine readable code controls the operation ofthe nodes 100. The machine readable code may be one or more programssuch as an operating system running one or more applications. Themachine readable code may also provide compression and decompression ofsurveillance information as will be described below. In one embodiment,the machine readable code is configured to allow a node 100 tocommunicate by unicast, multicast, or broadcast over a virtual matrixswitch.

In one or more embodiments, a node 100 comprises one or moretransceivers 320 configured for two-way communication in that eachtransceiver may receive and transmit information or data to one or moreother nodes 100 through one or more communication links 108, one or morenetworks 104, or a combination thereof. A transceiver may be configuredto communicate by unicasting, multicasting, or broadcasting informationthrough one or more wired or wireless connections. In some embodiments,one or more of the transceivers 320 may only transmit or only receivedata. It is contemplated that a transceiver 320 may also communicatewith other external devices as well as nodes 100.

In one or more embodiments, the one or more transceivers 320 may beconnected to one or more communication links 108. As stated above, thecommunication links 108 may be physical or wireless links and mayutilize one or more communication protocols.

As stated, wireless links in one or more embodiments may also comprise acellular link using various communication protocols. For example, atransceiver 320 may be configured to communicate through a TDMA, CDMA,FDMA, or other cellular network. A cellular communication link 108allows for long range wireless communication and provides the advantageof network availability even in remote areas. Though cellularcommunication links 108 may have limited bandwidth, the peer to peersurveillance architecture provides data compression to overcome thislimitation as will be discussed further below. It is contemplated that awireless communication link 108 may comprise wireless communication withone or more satellites and that wireless communication may beaccomplished through one or more antenna 324 if desired. The antenna 324may be internal to the node 100 or may be an external antenna connectedto the node 100.

As stated, each node 100 may have one or more communication links 108for redundancy. This may be accomplished by configuring a node 100 withmore than one transceiver 320, or by configuring a node with a singletransceiver capable of having more than one communication link. Only onecommunication link 108 is necessary for communication, thus anyadditional communication links 108 may be used to increase availablebandwidth such as by simultaneously utilizing all availablecommunication links 108 to transmit data, receive data, or both.However, a node 100 may also be configured to utilize the additionalcommunication links 108 only when the currently used link or links isdamaged or fails. Also, a node 100 may be configured to choose whichcommunication link 108 to use based on a predetermined order or based onthe available bandwidth, latency, or other characteristic of the links.

It is contemplated that any combination of communication links 108 maybe used by a single node 100. For example, a node 100 may have an IPcommunication link 108 through wired Ethernet, a cellular communicationlink, and a wireless 802.11 link simultaneously. One or more of thesecommunication links 108 may be used simultaneously or may remain unused(i.e. inactive) unless one or more of the other links is damaged orfails.

In one embodiment, the nodes 100 communicate through a communicationlink 108 using IP based communication. IP networks are inherentlyreliable and may be configured to automatically route data throughalternate links based on network congestion or availability. IP basedcommunication also allows multicasting which may be used to reducebandwidth utilization. In addition, a node 100 communicating via IP maycommunicate to or through any IP based device or network including theworldwide Internet. This allows nodes 100 to communicate around theworld with very little expense. Thus, IP networks are well suited for asurveillance application, however, it is noted that the peer to peersurveillance architecture may be used with any type of network orcommunication protocol.

In one or more embodiments, a node 100 also comprises a power source316. The power source 316 provides power to the node 100 so that it maybe used without being connected to an electric power grid. The powersource 316 may be any device capable of providing sufficient power for anode 100. Such devices include but are not limited to batteries, solarpanels, wind turbines, and generators or a combination thereof. In oneembodiment, a node 100 has a power source 316 comprising one or morebatteries and a solar panel which recharges the batteries. In anotherembodiment, a generator is provided which may power to node 100 directlyor be used to recharge any batteries the node may have. The generator orother power supply may be refueled periodically or as necessary toprovide power. It can thus be seen that a node 100 with a power source316 and a wireless communication link 108 may be quickly and easilydeployed virtually anywhere.

Components of the nodes 100 such as the processor 304, memory 308,storage 312, or transceivers 320 may communicate with one another in oneor more embodiments. In addition, the power source 316 component may beconfigured to communicate power utilization, power reserves, batterycondition, or other information in one or more embodiments. Componentsof the nodes 100 also include capture devices, screens, and controlinterfaces as will be described further below. It is contemplated thatother devices may be components of a node 100 such as but not limited toone or more lights or speakers.

In one or more embodiments, communication between components takes placethrough one or more optical, electrical, or wireless data connections.These connections may allow unidirectional or bi-directionalcommunication between the components. It is contemplated that in someembodiments, not every component will be connected to every othercomponent.

In one embodiment, only the processor 304 is connected to the memory308, storage 312, and one or more transceivers 320. In anotherembodiment, some components may be connected to more than one othercomponent. For example, the one or more transceivers 320 may beconnected to the memory 308, storage 312, or both, in addition to beingconnected to the processor 304. In this manner, the one or moretransceivers 320 may utilize the memory 308, storage 312, or bothwithout communicating with the processor 304. It is contemplated that insome embodiments, one or more components may communicate within the nodethrough a connection with another component.

In some embodiments, the components described above may be “off theshelf” products from various manufacturers. For example, a node may be acomputer having a processor 304, memory 308, storage 312, and one ormore transceivers 320 installed on a motherboard. In other embodiments,the components may be provided by one or more independent “off theshelf” products. For example, the processor 304, memory 308, and storage312 may be a computer or video processing device connected to anexternal camera, and one or more external transceivers 320. Theprocessor 304 may be a stand alone video processor such as, for example,a device which accepts video as an input and compresses, analyzes orotherwise processes the video and outputs the result. The storage 312may be comprise one or more stand alone storage devices such as, forexample, a set of hard drives, a RAID array, or USB or Firewire storage.It is contemplated that there may be more than one of each component forredundancy. Where more than one of the same component is included in anode 100, it is contemplated that each may be used simultaneously orthat one or more redundant components may remain inactive until needed.

It is contemplated that a node 100 may be located in mild environmentsand harsh or extreme environments (e.g. extreme heat, cold, moisture, orwind). Thus, each node 100 may be configured with various enclosures orstructures capable of supporting its components. For example, a node 100used indoors may have an enclosure as simple as an equipment rack orshelf. Alternatively, an indoor enclosure may fully enclose thecomponents of a node 100 such as with a metal, plastic, or other rigidcover. A node 100 for outdoor use may have a more rugged enclosure suchas by using stronger or thicker materials. In addition, some enclosuresmay have wind, water, ice, heat or other weather resistance. This may beaccomplished by insulating the enclosure and by including one or moreseals to prevent weather infiltration. Enclosures may include structuresthat do not fully enclose a node's components, and may includestructures now known and later developed, such as described below.

Generally, an enclosure will be a single continuous rigid structurewhich supports all the components of a node 100. A component of a node100 will be considered to be supported by the enclosure as long as thecomponent is ultimately supported by the enclosure. A component may besupported by the enclosure through one or more other structures. Forexample, a component held within or attached to its own case or supportis considered supported by the enclosure as long as its case or supportis attached to the enclosure.

Of course, in some embodiments, some components may not be supported orattached to an enclosure. For example, a camera may be attached directlyto a wall rather than to an enclosure. In addition, some enclosures mayhave portions that may be removably attached to allow for repair orreplacement. It is noted that, such enclosures are still considered tobe a single continuous structure because each removably attached portionwill be attached when the node is in operation. Various embodiments ofenclosures will be described further below.

Types of nodes will now be described. These nodes may include the basiccomponents of and may be configured according to the various embodimentsof the nodes 100 described above. In addition, the following nodesgenerally include additional components suited for one or more specifictasks in their various embodiments.

FIG. 4 illustrates an embodiment of a capture node 400 of the peer topeer surveillance system. Generally, a capture node 400 is a nodeconfigured to capture surveillance information from one or more targetareas. A target area is generally an area where useful surveillanceinformation may be gathered, but may be any area or location.Surveillance information may include video, audio, or both, as well asinformation from specific sensors such as voltage, current, temperature,radiation, motion, or light sensors. Surveillance information may alsoinclude information or data derived from the above information, or datareceived from an external source such as wireless stock ticker, traffic,GPS, or weather data.

In one or more embodiments, a capture node 400 may comprise a processor304, memory 308, storage 312, power source 316, one or more transceivers320, one or more antenna 324, or various combinations thereof asdescribed above. Regardless of the configuration, a capture node 400will generally include one or more capture devices 404 as one of itscomponents in one or more embodiments. Once captured, surveillanceinformation may be transmitted from the capture node 400 via its one ormore transceivers 320.

A capture device 400 is a device configured to receive, record, orotherwise capture surveillance information. The capture device 404 maybe integrated with one or more components of the capture node 400 in oneor more embodiments. For example, the capture device 404 may be a videocapture board. The capture device 404 may also be a stand alone devicein some embodiments. For example, the capture device 404 may be a cameraconnected to the processor 304 of the capture node 400. It iscontemplated that the capture device 404 may be movable (e.g. a pan,tilt, and zoom camera) to focus on specific events or areasperiodically, in response to an event, or as desired.

As stated, there is a wide variety of surveillance information, andthus, a similarly wide variety of capture devices 404 are contemplated.To illustrate, the capture device 404 may also comprise one or morecameras, microphones, temperature sensors, radiation detectors, motiondetectors. In addition, the capture device 404 may be a data input suchas for receiving telemetry from other devices. For example, the capturedevice 404 may be a radio receiver configured to receive traffic,weather, GPS, or even stock ticker information. The capture device 404may be a voltage or current sensor such as for detecting voltage orcurrent usage or for detecting a completed circuit such as in contactsensors for security systems.

In one embodiment, the capture node 400 is configured to capture videosurveillance information. As such, the capture node 400 has a capturedevice 404 comprising a video camera. The camera may be fixed or mayhave point, tilt, and zoom capability and may provide a video stream ofa target area. Pan, tilt, and zoom cameras may be moved to focus ondifferent areas as desired or according to a predetermined surveillanceplan. In addition, such a capture node 400 may be programmed toautomatically focus its camera (or other capture device) on an area inresponse to an event or notification or be remotely controlled such asthrough an external device or node in communication with the capturenode 400.

In one or more embodiments, a capture node 400 may compress thesurveillance information it is transmitting such as to save storagespace, to save bandwidth for multiple streams of information, or toallow transmission of data across low bandwidth communication links. Inone embodiment, a capture device 404 sends surveillance information to aprocessor 304 in the capture node 400. It is noted that the processor304 may process the surveillance information in a number of ways. Forexample, the processor 304 may analyze the information, as will bediscussed further below, or may compress the information.

In one or more embodiments, compression may occur through a compressionalgorithm or software comprising machine readable code stored on thememory 308, storage 312, or both. Any compression algorithm, now knownor later developed, that can be executed by the processor 304 may beused. Some examples of compression algorithms for various types of datainclude: H.261, H.264, G.711, ZIP, LZIW, JPG, MPEG-1, MPEG-2, andMPEG-4. It is noted that the compression algorithm used will depend onthe type of information to be compressed and the desired data rate,quality, or both of surveillance information after compression.

With regard to video surveillance, compression/decompression algorithmsor software known as a video codec, may be used to accept analog videoand then digitize, compress, and packetize it so it may be sent to itsdestination. Video compression and decompression requires significanthardware and software capabilities. In a worst case situation, where avideo scene has simultaneous background and foreground scene complexity(e.g. shapes and patterns that are dissimilar in color, texture, shape,hue, etc . . . ) and simultaneous 3-axis camera movement (e.g. pan, tiltand zoom all at the same time), along with 3-axis target movement (e.g.a suspect or vehicle moving at or away from the camera at a diagonal),the codec may be required to process as much as 6,400,000,000instruction sets per second or more. Traditional security industrycodecs will drop frames or produce DCT (Discrete Cosine Transfer)blockiness, or both, when subjected to such harsh conditions becausetraditional codec simply cannot process the instructions quickly enough.

Furthermore, conversion from analog to digital is done in “real time”where massive amounts of analog data are converted to digital in realtime. If the information cannot be processed quickly enough, some of thedata is thrown away (e.g. dropped frames) during the compressionprocess. The difference between the theoretical real time transformationand the actual transformation (the time delta) is called latency. Arespectable latency (from the capture of video to its subsequentviewing) for 4 CIF images at 30 frames per second is under 180milliseconds. If compression drops frames or introduces blockiness, thesurveillance information is largely worthless.

Thus, in one or more embodiments, a capture node 400 may include an ASIC(Application Specific Integrated Circuit) to meet the video compressionrequirements defined above. For example one or some of the processors304 of a capture node 400 may be ASICs designed to compress videoaccording to one or more types of compression as discussed above. Forexample, the ASIC may compress (and/or decompress) video according toone or more video codecs. It is contemplated that video and othersurveillance information may be compressed and decompressed through oneor more ASICs and that other nodes, besides capture nodes 400, mayutilize ASICs in one or more embodiments. It is contemplated thatcompression and/or decompression of surveillance information may beperformed, as described herein, on any node of the peer to peersurveillance architecture.

Each capture node 400 may transmit multiple streams of video or othersurveillance information, and each stream's network utilization may bemanaged differently. For example, a capture node 400 may set a firststream to 1 Mbps and UDP multicast, a second stream may be set for 256kbps and unicast, and so on. The network utilization of each stream ofsurveillance information may be set based on network capabilities (e.g.available bandwidth) or other conditions such as the monetary cost oftransmitting surveillance information over particular communicationlinks. It is noted that other nodes 100 of the peer to peer surveillancearchitecture may transmit multiple streams of surveillance informationas well.

In some embodiments, the capture node 400 may be configured to storecaptured surveillance information in addition to or instead oftransmitting it. The surveillance information may be compressed prior toits storage and may be written to the capture node's 400 storage 312,such as magnetic, optical, or flash media, if desired. Various forms ofstorage 312 may be utilized as will be described further with regard tothe content storage nodes of the peer to peer surveillance architecture.A capture node 400 may transmit live surveillance information, storedsurveillance information, or both alone or simultaneously, if desired.

It is contemplated that capture nodes 400 may be configured to analyzesurveillance information and provide one or more notifications if aparticular event is detected. For example, a capture node 400 may beconfigured to execute analysis software. This software may execute onone or more processors 304 of the capture node 400. Analysis ofsurveillance information and notifications are described further belowwith regard to the server nodes of the peer to peer surveillancearchitecture.

In one embodiment, the capture node 400 may be a cellular node. In thisembodiment, at least one transceiver 320 is configured to communicatethrough a cellular communication link or network. Cellular connectionsmay have reduced or limited bandwidth and thus compression may be usedto compress surveillance information before it is transmitted. Ofcourse, where there is sufficient bandwidth, uncompressed surveillanceinformation may be transmitted.

Video surveillance information from will generally be compressed priorto transmission over a cellular connection due to its higher bandwidthrequirements. As stated above, video compression may require significantprocessing power to provide video with a high frame rate, no artifacts,and no dropped frames. This is especially so on reduced bandwidthconnections such as cellular connections. Thus, though not required inall embodiments, it is contemplated that a cellular capture node 400 orother node having a cellular transceiver may include an ASIC configuredto compress video suitable for transmission over a cellular connection.

It is noted that a cellular transceiver 320 may communicate to othernodes 100 through the virtual matrix switch described above if desired.Thus, captured surveillance information may be unicast, multicast, orbroadcast to other nodes 100 through a cellular connection. This isadvantageous in a cellular connection (or other reduced bandwidthconnections) because multicast or broadcast transmissions allow multipleor all the nodes 100 to receive the same surveillance information from asingle transmission stream.

A cellular capture node 400, or other node having a cellulartransceiver, also has the advantage of being capable of having networkconnectivity in remote locations because its cellular transceiver 320may communicate over long distances wirelessly. Thus, it is contemplatedthat some embodiments of a cellular node may include one or more powersources 316 to allow the cellular capture node to operate without anywired connections. The cellular node may then be quickly and easilydeployed nearly anywhere by simply placing it where it can capturesurveillance information from one or more desired target areas.

FIG. 5 illustrates an embodiment of a viewing node 500. Generally, aviewing node 500 is used to view live and stored surveillanceinformation as well as control playback of live or stored surveillanceinformation. A viewing node 500 may also be used to select thesurveillance information to be viewed as well as various representationsor arrangements of the surveillance information. For example, thedesired live or stored video surveillance from one or more nodes may beselected and viewed on the viewing node 500. In addition, the viewingnode 500 may display other surveillance information in a table, graph,pie chart, text, or other arrangement.

It is contemplated that a viewing node 500 may also display or emitvarious alarms or warnings. For example, audible warnings, email alerts,and notifications of network or capture node failures may be presentedvisually or audibly via a viewing node 500. These alarms or warnings mayresult from one or more notifications transmitted by other nodes 100, asdescribed below, and received by the viewing node 500.

In one or more embodiments, a viewing node 500 may comprise a processor304, memory 308, storage 312, power source 316, one or more transceivers320, one or more antenna 324, or various combinations thereof asdescribed above. In addition, the viewing node 500 is a node and thusmay comprise any configuration described above with regard to FIG. 3. Aviewing node 500 may include one or more screens 504, control interfaces508, or both as components in one or more embodiments. It iscontemplated that a viewing node may be a personal computer (PC), smartphone (e.g. BlackBerry, iPhone), or personal media player in one or moreembodiments. As these devices are nearly ubiquitous, a further advantageof the invention is that surveillance information from any node may beviewed virtually anywhere.

The screen 504 may be a high resolution color display such as a computermonitor or LCD screen. Any type of screen 504 may be used with theviewing node 500. This includes but is not limited to televisionmonitors, black and white monitors, plasma and LCD screens, andprojectors.

In some embodiments, surveillance information from other nodes 100 isdisplayed on a screen 504 in a viewing pane 512 comprising a portion ofthe screen. As stated, the nodes 100 may be various combinations ofcapture, server, storage, and other nodes described herein. It iscontemplated that there may be one or more viewing panes 512 displayedon a screen 504 and that each viewing pane 512 may to displaysurveillance information from one or more nodes 100. A user may beprovided a list of nodes 100 and be allowed to select which node ornodes he or she wishes to view.

In one embodiment, the viewing panes 512 are displayed in variouslayouts such as 2×2, 3×3, 4×4, and 5×5. In other embodiments, theviewing panes 512 may be displayed according to a custom layout, such asshown in FIG. 5. For example, important viewing panes 512 may bedisplayed larger than other viewing panes. The viewing panes 512 to viewmay be selected from a list, map, or hierarchy of all available viewingpanes. In addition, viewing panes 512 may be assigned to one or moregroups and entire groups of viewing panes may be selected for viewingsimply by selecting the desired group. This may be used to viewsurveillance information from an entire site or salvo of nodes 100.

In one or more embodiments, surveillance information will be received bythe viewing node 500 through one or more transceivers 320 connected toone or more communication links 108. It is noted that each viewing node500 may also transmit data such as to initiate communications with othernodes 100, request surveillance information, and control capture nodecameras or other capture devices. The viewing node 500 may also outputor export surveillance information so that it may be recorded by anexternal device. For example, video surveillance information may beexported to a video file, or may be output to a VCR, DVD, or otherrecording device or media for recording. It is contemplated thatsurveillance information may be exported to industry standard formatsand be watermarked or signed to ensure its authenticity. Other nodes mayalso export surveillance information.

As stated, surveillance information may be uncompressed or compressed.Where the surveillance information is compressed, the viewing node 500may decompress the surveillance information before it is viewed. Thismay occur by the processor 304 executing one or more decompressionalgorithms on the incoming surveillance information.

Of course, the proper decompression algorithm must be determined andsuch determination may occur by a handshake communication where one nodenotifies another of the algorithm it is using to compress information.The proper algorithm may also be determined by a node analyzing theincoming surveillance information. In some embodiments, a node maypresent the compression types it is capable of decompressing and thesource node may select a compression algorithm accordingly. In essence,nodes may agree on which compression algorithm to use. It iscontemplated that the communication of any type of surveillanceinformation between any nodes of the peer to peer surveillancearchitecture may be facilitated by the handshake communication.

In addition to viewing panes 512, a viewing node 500 may displaysurveillance information on a timeline. In this manner, surveillanceinformation is generally displayed according to the time it was capturedor recorded. The timeline may have a resolution from one second to onemonth, but this range of resolution may be increased or decreased in oneor more embodiments. The timeline provides the advantage of allowingsurveillance information to be viewed together with the time it wascapture or corresponding to other times. In this manner, more than onestream or type of surveillance information may be viewed such that anysurveillance information for a particular time may be viewed together.For example, a video may be viewed synchronized with telemetryinformation, audio, or even other video. The timeline may be scrolledacross the screen 504, or set to a specific start time, end time, orboth.

In one or more embodiments, a viewing node 500 may include one or morecontrol interface 508. A control interface 508 has the advantage ofspecific buttons, switches, or other controls not commonly found on akeyboard or mouse. In one embodiment, a control interface 508 may havemedia player type controls such as play, pause, fast forward, rewind,single frame advance or reverse, slow motion forward or reverse play,and stop. In addition a jog shuttle may be provided in some embodiments.The jog shuttle may be a circular knob which, when turned, allows finecontrol of the speed of the forward or reverse playback of surveillanceinformation.

The playback or display of surveillance information on each viewing pane512 may be individually controlled by the control interface 508. Inaddition, the controls may be used to control other aspects of viewingsuch as the volume of audio, or the magnification (i.e. zoom) of video.In one or more embodiments, signals comprising instructions to controlthe display of surveillance information, are generated from theoperation of the control interface 508 and received by controlinterface's attached node.

In one embodiment, one or more of the viewing panes 512 is used to viewvideo surveillance information. In this embodiment, available videosurveillance information may be selected for viewing. The videosurveillance information may be listed for selection with a text orother label, a thumbnail, or both. Each list item corresponds to thesurveillance information provided by a particular node 100 or nodes. Forexample, a list item labeled “Building 10 Northeast Corner” maycorrespond to a capture or other node on the northeast corner ofBuilding 10. Based on this, a user may then choose one or more videosfor viewing as he or she desires. It is noted that other types ofsurveillance information may be similarly listed for selection with atext or other label, thumbnail, summary, or combination thereof.

In one or more embodiments, a viewing node 500 may be configured tostore the last 30 seconds of surveillance information received by theviewing node on its storage 312, memory 308, or both. For example, thelast 30 seconds of live video surveillance may be stored so that a usermay easily review the last 30 seconds of events. In some embodiments,this storage of video or other surveillance information is temporary andmay be more or less than 30 seconds if desired.

FIG. 6 illustrates an embodiment of a content storage node 600.Generally, a content storage node 600 is configured to storesurveillance information captured or transmitted from other nodes 100,and to transmit stored surveillance information to other nodes. Theseother nodes 100 may be any type of node including but not limited tocapture nodes, viewing nodes, or even other storage nodes.

In one or more embodiments, a content storage node 600 may comprise aprocessor 304, memory 308, storage 312, power source 316, one or moretransceivers 320, one or more antenna 324, or various combinationsthereof as described above. Generally, content storage nodes 600 willinclude storage 312 to store the surveillance information received fromother nodes 100.

The storage 312 in one or more embodiments is one or more hard drives.The hard drives may be configured in a RAID configuration, such as RAID1 or RAID 5, in one or more embodiments. Of course various forms ofstorage 312 may be used. For example, the storage 312 may be internal orremovable optical, magnetic, or flash media. In some embodiments, thestorage 312 may be written to only once such as with DVD-R or CD-Rtechnology. In other embodiments, the storage 312 may allow repeatedreading and writing such as with a hard drive or other magnetic media.

A content storage node 600 is capable of storing both compressed anduncompressed surveillance information. For example, the content storagenode 600 may receive compressed video from another node 100. Wherecompressed surveillance information is received it may be directlystored or, if desired, the content storage node 600 may decompress theinformation before it is stored. In addition, uncompressed surveillanceinformation received by the content storage node 600 may be directlystored or compressed before it is stored. Compression will generallyoccur through one or more compression or decompression algorithmsexecuted on the processor 304 as described herein. In addition, contentstorage nodes 600 may also go through a handshaking process with othernodes as described above. In this manner, the content storage nodes 600may agree upon a compression/decompression algorithm for a particulartransmission of surveillance information.

A content storage node 600 may be configured to transmit storedsurveillance information in one or more embodiments. Surveillanceinformation may be transmitted in compressed or uncompressed formregardless of how it has been stored. In addition, it is contemplatedthat surveillance information stored according to one type ofcompression may be recompressed with another type of compression priorto its transmission. This is advantageous in that it allows surveillanceinformation to be compressed with another type of compression that mayhave reduced bandwidth requirements. In addition, some nodes may notsupport all compression types. Thus, the content storage node 600 mayrecompress surveillance information according to a compression typesupported by the nodes it is communicating with. Of course, compressedsurveillance information may be decompressed and transmitted asuncompressed surveillance information.

One advantage of a content storage node 600 is that surveillanceinformation may be stored in multiple physical locations. For example, acapture node may transmit surveillance information to a plurality ofcontent storage nodes 600 in various locations. In this manner, thesurveillance information is preserved even if one or more of the contentstorage nodes 600 is damaged or destroyed. Similarly, surveillanceinformation may be retrieved from multiple physical locations. Forexample, if connectivity to a geographic region, building, office, orother physical location is reduced or unavailable, the desiredsurveillance information may be retrieved from a content storage node600 in a different physical location.

FIG. 7 illustrates an embodiment of a server node 700. Generally, aserver node 700 is configured to provide services related toauthenticating access to and analyzing surveillance information. Theserver node 700 may be configured to authenticate requests for or accessto surveillance information, analyze live or stored surveillanceinformation, or both.

In one or more embodiments, a server node 700 may comprise a processor304, memory 308, storage 312, power source 316, one or more transceivers320, one or more antenna 324, or various combinations thereof asdescribed above. In addition, the server node 700 is a node and thus maycomprise any configuration described above with regard to FIG. 3.

In one embodiment, the server node 700 provides authenticationcapability. The server node 700 may use commercial software toaccomplish this, such as Active Directory authentication in MicrosoftWindows. Of course, the server node 700 does not have to utilize ActiveDirectory as it is contemplated that any system, now known or laterdeveloped, where one or more user or other access accounts may bemanaged and authenticated through one or more server nodes 700 may beused with the peer to peer surveillance architecture.

In a peer to peer configuration, the server node 700 may validate auser's or a device's credentials and allow or deny access to the peer topeer surveillance architecture accordingly. In one or more embodiments,this may occur by the server node 700 returning a key or code whichallows access to other nodes 100 of the surveillance architecture. Eachnode may be configured to respond only to one or more particular keys.It is contemplated that, in one or more embodiments, the keys may begenerated through use of digital signatures, encryption, hashingalgorithms, or both, now known or later developed, such as in a publickey infrastructure.

The server node 700 may also be used to manage user or other accessaccounts such as by assigning access privileges or restrictions to auser other account or to a group of accounts. The privileges orrestrictions may be set on the server node 700 to vary depending on theparticular node 100 or group of nodes being accessed.

In embodiments of the peer to peer surveillance architecture whereauthentication is required for access, it is contemplated that aplurality of server nodes 700 providing authentication services may beused for redundancy. These server nodes 700 may be deployed in differentphysical locations to increase reliability as described above. It iscontemplated that changes to user or other accounts may occur throughany server node 700 which then may update other server nodes within thesurveillance architecture accordingly.

In one embodiment each node 100 may be configured with one or moreaccess codes or usernames and passwords which allow access to a node ifcorrectly presented to the node. This embodiment does not require aserver node 700 as each node 100 may authenticate access requestsitself. One or more server nodes 700 may be utilized to manage user orother access accounts for each node 100 in this embodiment however.

One advantage of authentication is that each user or device may havetheir own accounts. This allows different access levels depending on theuser or device and prevents the entire peer to peer surveillancearchitecture from being compromised if one or more access codes arerevealed. Access codes may be changed as desired to further enhance thesecurity of the surveillance architecture. Though this may beimplemented at each node 100, use of one or more server nodes 700providing authentication services has several advantages. One advantageis that accounts and access codes may be created, modified, or deletedat any server node 700. Each server node 700 may synchronize account andaccess code information to provide full redundancy for theauthentication services.

Another advantage is that the server nodes 700 may be configured to logand audit access requests or other authentication activities. All userand system activity may be collected in the audit log along with thetime at which the activity occurred. For example, a user's viewing oflive or recorded surveillance information may be logged in the auditlog. In this manner, a security audit may be performed on the peer topeer surveillance architecture to ensure its integrity. The audit logmay be mirrored or copied to other server nodes 700, content storagenodes, or other nodes having storage for redundancy.

Server node based authentication is particularly useful in largesurveillance architectures, such as city-wide surveillance architectureswith hundreds to thousands of users and nodes. Managing access toindividual nodes 100 may occur at each node, such as by setting up useror device accounts on each node. However, it is much easier to manageaccess to the nodes 100, especially in large surveillance architectures,from the one or more server nodes 700.

In one or more embodiments, a server node 700 may be configured toprovide analysis of surveillance information it receives. This analysiswill generally be performed through analysis software or machinereadable code executing on one or more processors 304. With regard tovideo surveillance information, a server node 700 may accept an incomingvideo stream to detect one or more events such as by analyzing the videoto detect or recognize motion, images or particular events. In addition,the server node 700 may have software capable of creating virtualtripwires, detecting objects that have been left behind by one or moresubjects. Any analysis software may be used, and thus a variety ofanalysis may be performed including license plate and facialrecognition. Software requiring specific video formats may be utilizedas well because the server node 700 may request video of a specificformat, such as a specific video format or compression type, from theother nodes 100. In addition, it is contemplated that the server node700 may convert incoming video to a format usable by the analysissoftware if necessary.

The server nodes 700 may also provide analysis of other surveillanceinformation to detect particular events therein. For example, weatherinformation may be collected by various capture nodes and analyzed totrack temperatures, wind speed, humidity, or other data for a geographicarea. Each server node 700 may be configured to perform one or moreanalysis services of other server nodes 700. In this way, redundancy isprovided for any analysis service used by the peer to peer surveillancearchitecture. In addition, one or more server nodes 700 may worktogether to analyze a particular stream or set of surveillanceinformation. The results of the analysis of surveillance information maybe stored on the server node 700, content storage nodes, or even othernodes.

In one or more embodiments, users may setup triggers which are activatedwhen particular events are detected. For example, one or more servernodes 700 may be configured to notify one or more users when aparticular event is detected. Notification may occur by email, phone,text messaging, on screen dialogs, sounds, or other methods. It is notedthat each server node 700 may provide different analysis services andhave different triggers and notification settings. One or more contentstorage nodes may be configured with analysis, triggering, andnotification capabilities as well, in one or more embodiments.

In addition to notifying users, other nodes may be notified whenparticular events occur. For example, capture nodes with cameras may benotified to zoom in or focus on an area when a virtual tripwire istripped or when a particular event is detected. Notification of anothernode may occur by one node communicating a notification messageincluding information regarding an event to another node. The detectionof an event includes recognizing animate or inanimate objects and maytrigger further analysis by the same or one or more other server nodes700. It is noted that any node may provide notification, such as forexample, a node providing a notification of a communication linkfailure, or hardware or software failure.

It is contemplated that the peer to peer surveillance architecture mayinclude one or more hybrid nodes in some embodiments. A hybrid node maycombine components of the types of nodes described above. For example,in one embodiment, a capture node may include storage as described withregard to a content storage node, or vice versa. In other embodiments,the capture node may include a screen for viewing captured surveillanceinformation, or may provide authentication services, analysis services,or both. In yet another embodiment, a viewing node may be configured toprovide analysis services. The above listing of exemplary hybrid nodesis not intended to be exhaustive or limiting, as a wide variety ofhybrid nodes may be formed from the components of the nodes disclosedherein.

As stated, peer to peer means that each node within the surveillancearchitecture operates independent from (i.e. does not rely on) its peernodes. In traditional surveillance systems, a central control device orcontroller aggregates incoming surveillance information and, if soconfigured, also sends control instructions to its connected capturedevices. This creates a single point of failure because each capturedevice relies on a single central controller in order to function. Thisalso limits the number of capture devices and simultaneous users to thecapacity of the control device. In contrast, the peer to peersurveillance architecture does not rely on any central control device aseach node is independent.

To illustrate, failure to receive video surveillance from a surveillancecamera can be due to various causes. For example, the cable from thecamera may be damaged, the device receiving video surveillance maymalfunction, or the camera itself may be malfunctioning. In atraditional system with central control, any one of these problemsprevents the capture and use of surveillance information because thecentral controller is not receiving any surveillance information.

With the peer to peer surveillance architecture herein: where there is adamaged cable, a capture node may utilize one or more redundantcommunication links; where a viewing node is malfunctioning, a user maysimply use another viewing node; and where the capture node ismalfunctioning a redundant capture node at the same location may beused. As stated, a viewing node may be a PC, smart phone, or personalmedia player in one or more embodiments, and thus, switching to anotherviewing node is easily accomplished within the peer to peer surveillancearchitecture.

Furthermore, capture nodes may store the surveillance information theycapture or transmit to other nodes for analysis, storage or both. Thus,in the unlikely event that a user cannot view surveillance informationthrough a viewing node, the captured surveillance information is notlost. Though the user is temporarily unable to view the surveillanceinformation, he or she may still be notified by one or more server nodesanalyzing the information for particular occurrences, and theinformation may be stored for later review by the user.

It is noted again that, users and viewing nodes (and any other node) maybe in different geographic locations and use more than one completelyindependent network to communicate. Thus, the failure of a cable or evenan entire network in one or more locations does not prevent the peer topeer surveillance architecture from operating. For example, a singlenode may have a cable Internet connection, a cellular connection, and anISDN connection.

The nodes themselves may have redundant components. For example, acapture node may have more than one camera or other capture device, or acontent storage node may be configured with a RAID storage array. It iscontemplated that a node may be configured such that each component hasa backup or redundant counterpart. Such redundancy is not available intraditional systems.

A highly available surveillance system includes devices that have a highMean Time Between Failure (MTBF), and Mean Time Between Critical Failure(MTBCF). As discussed above, the peer to peer relationship between nodesensures no loss of service during a node, communication, or networkfailure. However, after a failure and until the failed node,communication link, or network is fully operational the peer to peersurveillance architecture may be operating under less than optimalconditions. For example, redundant communication links may have lessbandwidth and more latency, or be more expensive. Also, where therealready has been a failure, an additional failure may result in loss ofsurveillance capability. Thus, the peer to peer surveillancearchitecture provides another advantage in that it has a low Mean TimeTo Repair (MTTR) in one or more embodiments.

As an initial matter, the nodes themselves may be configured withcomponents having a high MTBF and MTBCF to reduce failures and the needfor repairs. Various node configurations, protective components, andenclosures may be used to protect node components from environmentalthreats which may lower a component's MTBF or MTBCF, such as high or lowtemperatures, power surges, lightning, and humidity.

In addition, nodes may be configured to allow access by qualifiedtechnical or other personnel. This access to a node is highlyadvantageous in maintaining and repairing individual nodes. In one ormore embodiments, operating information including information regardinghardware and software abnormalities or failures may be stored by thenodes. This information can be used to prevent node failures, such as byallowing preventative maintenance to occur, as well as to optimize nodeperformance. It is contemplated that the nodes may have internaldiagnostics and may allow technicians or other personnel to accessoperating information, change hardware or software settings, or rundiagnostics through a diagnostic connection with the node. Thediagnostic connection may be authenticated and occur through one or morecommunication links, networks, or a combination thereof as discussedabove.

The diagnostic connection allows quick diagnosis over a remote or directconnection to reduce a node's MTTR. Repairs, such as changing hardwareor software settings may be implemented through the diagnosticconnection as well. Where replacement hardware is necessary, thediagnostic connection may be used to quickly identify what hardware tobe replaced.

It is noted that, because the nodes are independent, a repair may occursimply by replacing a damaged node with a new one. While the new node isin place, the damaged node may be diagnosed and repaired. It iscontemplated that configuration settings for a node may be savedexternal to the node or exported from the node and imported into asimilarly configured node to allow for rapid replacement of individualnodes.

In one or more embodiments, diagnosis of software or hardware issues mayoccur through one or more diagnostic routines or programs. Generally,these routines or programs input data into one or more of a node'scomponents and confirm that the corresponding output from the componentsis as expected or within an acceptable range for a properly functioningcomponent.

The peer to peer surveillance architecture has another advantage in thatmaintenance updates or upgrades may be performed without impacting theoverall surveillance architecture. This is because each node may beindividually updated or upgraded without interrupting the operation ofany other node. It is noted that, in contrast to an unplanned failure,updates and upgrades may be planned in advance so as to occur whenoperation of a particular node is not crucial. Updates include firmwareor other software updates for a node's components, and may includereplacement of components with new revisions of the same. Upgradesgenerally may be thought of as software or hardware replacements thatincrease the node's or a particular component's capabilities orcapacity, reduce power consumption, or provide other benefits.

As stated various enclosures may be used to support and/or protect thecomponents of various nodes of the peer to peer surveillancearchitecture. In one embodiment, enclosures may be configured to protectnode components from natural, man-made and other hazards that coulddamage a node. For example, an enclosure may provide protection fromwater, humidity, wind, temperature, fire, radiation, electromagneticinterference, high voltage, physical damage or a combination thereof. Inone or more embodiments, an enclosure may protect the components thereinby providing a physical barrier to one or more hazards. It is noted thatthe enclosure is generally described herein with regard to asurveillance node. However, it is contemplated that the enclosure may beused with and benefit other surveillance hardware or devices.

An enclosure may also provide an environmentally controlled operatingenvironment for a node's components. For example, an enclosure maycontrol humidity, temperature, dust or other particulate concentrations,or a combination thereof for the components of a node. This isadvantageous in that it provides an operating environment suited to thecomponents. To illustrate, in one embodiment, the enclosure controls thetemperature within a node to prevent temperatures that are excessivelycold or excessively hot for the node's components.

FIG. 8A illustrates an exemplary embodiment of an enclosure 804 for anode 100. As shown, the enclosure 804 is rectangular in shape. It willbe understood that the enclosure 804 may be various shapes in one ormore embodiments. For example, the enclosure 804 may be square, round,rounded, or comprise a combination of various shapes. An enclosure 804may also be various sizes. In one or more embodiments, the size of anenclosure 804 may be determined based on the components to be storedtherein. The embodiment shown also includes a dome 808 for a camera. Itis noted that a dome 808 may not be provided in embodiments withoutcameras.

The structure of an enclosure 804 may be formed from various materials.Typically, the enclosure 804 will be a rigid structure to allow theenclosure to support a node's components. For example, the enclosure 804may be formed from one or more metals, alloys, plastics, carbon fiber,or a combination thereof. It will be understood that other suitablerigid materials may be used as well.

In addition, an enclosure 804 may be formed from materials configured orselected to protect a node's components. For example, one or more rigidmaterials, such as those described above, may be used to protectcomponents from physical hazards such as but not limited to water,humidity, dust and other particulates, physical impact or force, or acombination thereof. It is contemplated that the enclosure 804 may beconfigured to withstand significant physical impacts in someembodiments. For example, the enclosure 804 may be bulletproof/resistant. In addition, an enclosure 804 may be formed frommaterials, such as metallic or insulating materials, that protect thecomponents from other hazards such as but not limited to radiation,temperature, electromagnetic interference, and electrical charges.

In one or more embodiments, the enclosure 804 may be formed from amulti-layered material. A cross section of such a multi-layered materialis illustrated in FIG. 8B. It is contemplated that an enclosure 804 maybe formed from various rigid, insulating, protective and other layers ofmaterial. Each layer may have the same or a different thickness. It willbe understood that the thickness of a layer may be selected based on thedesired protective characteristics, rigidity, or both. For example, athicker metal layer may provide increased rigidity. The exemplaryembodiment of FIG. 8B illustrates an enclosure formed from amulti-layered material comprising a coating layer 816, an aluminum layer820, an insulating layer 824, and a foil layer 828.

It will be understood that each layer of material may be included in anenclosure for one or more protective, insulating, or othercharacteristics of the material. In the exemplary embodiment of FIG. 8,the coating layer 816 may provide protection from UV light, provide somethermal insulation from external sources of heat, or both. The coatinglayer 816 may also protect other layers from oxidation and be variouscolors. It is contemplated that the coating layer 816 may be variouspaints or other coatings in one or more embodiments.

The aluminum layer 820 may provide electromagnetic shielding as well asprovide a rigid physical structure to support components of a node andto protect such components from physical damage. The insulating layer824 may be foam or other insulation that helps regulate temperaturewithin the enclosure. Finally, the foil layer 828 may provide thermalinsulation, electromagnetic shielding, or both.

It is noted that various portions, such as the chambers that will bedescribed below, of an enclosure 804 may be formed from differentlayers, materials, or both. To illustrate, the enclosure 804 shown isformed from a two-layered material in one portion and a four-layermaterial in another portion. This is advantageous because it allows theenclosure 804 to provide protection suited to particular components. Forexample, certain components may not require as much or any thermal,electromagnetic, or other protection and thus the portion or portions ofthe enclosure 804 where these components are located may be formed fromdifferent materials or layers than other portions of the enclosure. Thisalso prevents waste of materials because a layer of material may only beincluded when needed.

As illustrated in FIGS. 8A and 8D, an enclosure 804 may comprise one ormore chambers. In general, the chambers allow one or more components ofthe nodes to be stored and protected therein. In one or moreembodiments, one or more chambers may be sealed such that they are airtight, water tight, or both. This is advantageous in that a sealedchamber fully encloses the components therein and prevents infiltrationof water, moisture, and dust and other particles. In addition, a sealedchamber allows a temperature range to be more easily maintained withinthe chamber because air of various temperatures cannot infiltrate thechamber. Each chamber may be formed from the same or different single ormulti-layer materials.

As illustrated in FIG. 8C, a chamber may have one or more openings toallow electrical, optical, or other connectors 840 to accept an externalconnection. If desired (or required such as in the case of a sealedchamber), the connectors 840 may have a sealed bulkhead to prevent air,moisture, water, dust or other particles, or a combination thereof frominfiltrating a chamber through the connectors. In general, a sealedbulkhead allows a portion of an electrical, optical, or other conductoror connection to be externally accessible while preventing air or waterinfiltration by sealing the space around the conductor or connection.For example, in an electrical connector, any space around eachelectrical lead may be sealed or blocked by a portion of the connectorsuch as the body of a connector.

In one or more embodiments, a chamber may also have one or moreremovable portions 812 to allow access to the components or parts withina chamber. It is contemplated that a removable portion 812 may be takenoff a chamber to allow a technician or other person to access the insideof a chamber. This is advantageous in that such access allows componentsor parts to be repaired, replaced, updated, upgraded, removed,reinstalled, and the like. This also allows the inside of a chamber tobe cleaned if needed or desired.

As can be seen in FIGS. 8A and 8C, the removable portion 812 may be apanel, door, or similar structure. The removable portion 812 may besecured to a chamber in various ways. For example, one or morefasteners, such as but not limited to screws, clips, clamps, pins, hookand loop, magnets, or a combination thereof may be used to secure theremovable portion 812. In some embodiments, the removable portion 812may be completely removable. For example, the removable portion 812 ofFIG. 8A may be completely disconnected from an enclosure 804 by removingthe screws. In other embodiments, the removable portion 812 may bepartially removable. For example, the removable portion may be securedto an enclosure 804 by one or more hinges, slides, hooks, or the like.

The removable portion 812 may be formed from the same single ormulti-layer material as its chamber. This allows the removable portion812 to have the same protective characteristics as the remainder of thechamber. For example, the removable portion 812 may have the same orsimilar electromagnetic, heat, or other shielding as its chamber. Inthis manner, when the removable portion 812 is fastened or secured tothe chamber, the components or parts within the chamber are protected asthough the chamber did not have an opening. It is noted that theremovable portion 812 may form an air or watertight seal in embodimentshaving sealed chambers. It will be understood that one or more gasketsor other seals may be used to form such a seal between a removableportion 812 and a chamber. If desired, one or more connectors may besecured to a removable portion 812 of a chamber.

In the embodiment of FIG. 8A, the enclosure 804 comprises two chambers,a component chamber 832 and a support chamber 836. In one or moreembodiments, the component chamber 832 may contain components of thenodes as described above while the support chamber 836 may contain partsfor regulating or controlling environmental factors within an enclosure804, or portions thereof. The support chamber 836 may also provide powerand other resources necessary to allow node components to operateproperly.

As the cross section view of FIG. 8D shows, the support chamber 836 maybe formed from a different multi-layer material than the componentchamber 832. In the exemplary embodiment of FIG. 8D, the support chamber836 is formed from a multi-layer material comprising a UV coating layer816 and an aluminum layer 820 while the component chamber is formed froma multi-layer material comprising a UV coating layer, an aluminum layer,an insulating layer 824, and a foil layer 828. As can be seen, thesupport chamber 836 comprises vents 848 to allow the passage of air,while the component chamber 832 is sealed.

It is noted that an enclosure 804 may also provide one or more mounts844, as shown in FIG. 8C, to allow the enclosure to be attached orsecured to a wall, pole, or other structure. It is contemplated thatvarious mounts 844 may be provided for various mounting applications.

The support chamber 836 will now be described with regard to FIG. 9.FIG. 9 is a cross section view of an exemplary support chamber 836having parts for regulating or controlling the environment in andproviding power to one or more component chambers 832 or other chambers.

Power may be provided via a power supply 920 within the support chamber836. In one or more embodiments, a power supply 920 accepts power andconverts it such as by raising or lowering the voltage/amperage so thatit is usable by the components or parts. The power supply 920 may alsoconvert AC power to DC power and vice versa in some embodiments. It iscontemplated that the power supply 920 may accept a wide range of inputvoltages and convert the same to usable voltages. In one embodiment, theinput voltage acceptable to the power supply 920 is between 90-270 VAC.The power supply 920 may be configured to operate in a wide range ofenvironmental conditions such as in extremely cold or extremely hotenvironments, or in between.

The power supply 920 will typically, but not always, receive power froman external source such as a power grid. In embodiments where a nodeincludes a power source for generating its own power, the featuresdescribed above may be incorporated into the node's power source.Alternatively or in addition, a power supply 920 may be connected to anode's power source. It is noted that a nodes' power source may belocated in a support chamber 836 in one or more embodiments.

The power supply 920 may be secured within a support chamber 836 invarious ways. As shown in FIG. 9, the power supply 920 is mounted to apower supply mount 960 having a rigid structure which raises the powersupply above the bottom of the support chamber 836. This allows coolingairflow to reach more of the power supply's surfaces to better cool thepower supply. Of course, a power supply 920 may be secured in variousother ways. For example, a power supply 920 may be secured directly to aportion of the support chamber 836 by one or more fasteners orstructures.

The support chamber 836 and parts therein may be configured to controlthe environment of another chamber, such as a component chamber 832. Inone or more embodiments, the environment may be controlled throughvarious environmental control devices which control temperature,humidity, particulate concentration, or other characteristics of the airor other gas within an enclosure. For example, fans, refrigeration orother cooling devices, heating elements, heatsinks, thermal conductors,dehumidifiers, or a combination thereof may be used control theenvironment within an enclosure. This is advantageous because sealedcomponent chamber or other chamber may require a temperature controlledenvironment in one or more embodiments to prevent excessively hot orexcessively cold temperatures from hindering operation of, damaging, ordestroying components of a node. It is noted that the environment withinthe support chamber 836 may also be controlled by the support chamber inone or more embodiments.

In the exemplary embodiment of FIG. 9, the support chamber 836 comprisesan airflow system and a thermal conductor 916 to control the environmentof one or more chambers. In general, the thermal conductor 916 is acomponent which transfers heat from another chamber by conducting heataway from the other chamber. This allows the thermal conductor 916 tocool the other chamber. In general, the airflow system generates airflowto cool the thermal conductor 916. The airflow helps dissipate heat fromthe thermal conductor 916 allowing the thermal conductor to transferheat more quickly.

The thermal conductor 916 may be configured in various ways. In oneembodiment, the thermal conductor 916 may have a first portion forabsorbing heat and a second portion for dissipating heat. Typically, theportion for absorbing heat will be in physical contact with the chamberthe thermal conductor 916 is cooling. For example, the thermal conductor916 may be in physical contact with a component chamber 832 to cool thecomponent chamber. In one or more embodiments, the portion for absorbingheat may protrude into the chamber that is to be cooled, such as shownin FIG. 9. In this manner, heat may be absorbed from the chamber to coolthe chamber.

To allow the thermal conductor 916 to protrude into a chamber, it iscontemplated that a chamber, or a portion thereof, may have one or moreopenings. The chamber may form a seal around the thermal conductor ifdesired. In this manner, a sealed chamber can remain sealed even thoughthe thermal conductor 916 is protruding into the chamber. In oneembodiment, an opening large enough to accept a thermal conductor 916may be provided. In other embodiments one or more openings large enoughto accept one or more portions of a thermal conductor may be provided.For example, a thermal conductor 916 may be in two (or more) sectionswith a first section being in the support chamber 836 and a secondsection in another chamber. The sections may be connected through one ormore openings in a chamber by one or more fasteners such as screws orthe like, one or more heat conducting materials, one or more heat pipes,or other members.

The thermal conductor 916 may be formed from materials, now known orlater developed, which conduct heat. Typically, the materials withadvantageous heat conducting properties will be used. For example, rigidmaterials, such as copper, aluminum, gold, steel, other metals, or acombination thereof may be used to form a thermal conductor 916. Athermal conductor 916 may include one or more heat dissipation fins,such as those found on heat sinks, at various locations to dissipateheat, absorb heat, or both. In addition, a thermal conductor 916 mayinclude elements for liquid cooling. For example, the thermal conductor916 may have one or more channels for liquid coolants. In oneembodiment, the thermal conductor 916 includes one or more liquid filledheat pipes to transfer heat through the thermal conductor.

In one or more embodiments, the thermal conductor 916 may comprise anactive or powered element for transferring heat from another chamber orto cool another chamber. For example, the thermal conductor 916 maycomprise a Peltier device in one or more embodiments. Typically, thePeltier device will be oriented such that its cooler side is facing, incontact with, or inside the chamber to be cooled while its hotter sideis within the support chamber 836. In this manner, heat may be absorbedby the cool side and dissipated in the support chamber 836. In addition,the cooler side of the Peltier device may be used to cool the supportchamber 836 while the Peltier's hotter side is cooled by the supportchamber 836. It will be understood that embodiments utilizing a Peltierdevice may include the dissipation fins, liquid cooling structures, heatpipes, heat sinks, or a combination thereof as described above. It iscontemplated that the Peltier device may have one or more fans attachedto its cool side to move cooled air within a chamber thereby cooling thecomponents within such chamber.

As stated, the thermal conductor 916 (as well as other parts) may becooled by the airflow system. The airflow system may be configured toensure to reduce or eliminate degenerative airflows within a chamber.Generally, degenerative airflow is airflow that prevents the airflowsystem from accomplishing the desired results. Usually, degenerativeairflows are created during an exception or problem condition. Forexample, a fan failure when two exhaust fans are used in parallelcreates degenerative airflow because airflows may cycle from the failedfan to the operating exhaust fan directly without reaching the rest of achamber or enclosure. In one embodiment, as will be described below, theairflow system utilizes fans positioned in series to prevent such anoccurance.

In general, the airflow system generates airflow between an air inlet928 and an air outlet 932 of a support chamber 836. The inlet 928 andoutlet 932 may comprise one or more openings, such as louvered orun-louvered vents 848, in the support chamber to allow the passage ofair. In one embodiment, the inlet 928 and outlet 932 may be sized toregulate the air pressure within the support chamber 836. For example,the inlet 928 may be sized larger than the outlet 932 to allow more airto flow into the support chamber 836 than out. In this manner, apressure head may be formed to ensure positive airflow within thesupport chamber 836. The positive airflow provides cooling and reducesor prevents a buildup of airborne particles inside the support chamber836.

Airflow may be generated by various devices. For example, one or morefans, blowers, electrostatic air movers, or the like may be used togenerate airflow. In one embodiment, the airflow system comprises a fanassembly 924 that generates airflow between the air inlet 928 and theair outlet 932. The fan assembly 924 itself may be configured in variousways. As shown in FIG. 9 for example, the fan assembly 924 comprises twofans 904 which are positioned in series by a spacer 912. In thisconfiguration, the fans 904 are aligned in series by their axis ofrotation. Typically, both fans 904 will spin in the same direction togenerate airflow in the same direction. This allows each fan 904 toprovide the same direction of airflow in case one fan fails.

Positioning of the fans 904 in series also ensures that no degenerativeairflows are created by the failure of a fan. As can be seen, thefailure of one fan 904 does not provide an alternate route through whicha degenerative airflow can flow. This is because another fan 904 ispositioned to prevent such degenerative airflow.

The spacer 912 may be configured as an open hollow structure having twoopen ends to which fans 904 may be attached. The spacer 912 may be sizedsuch that the fans 904 are spaced apart to prevent shock waves from thefans' blades from negatively impacting the performance of the fans. Forexample, the spacer 912 may be sized based on the length, width, orother characteristic of a fan's blades to reduce or eliminate the impactof shock waves on fan performance. In one embodiment, the spacer 912 mayprovide an airtight seal between fans 904. This ensures airflow isdirected where desired. Spacing and sealing of the fans also ensuresthat the desired amount of backpressure (i.e. resistance to airflow)within the support chamber is maintained.

One benefit of a plurality of fans 904 is that failure of a single fandoes not cause the entire airflow system to fail as one or more otherfans may continue to move air. Of course, a single fan 904 or more thantwo fans may be used in some embodiments. Where a plurality of fans 904are provided, the fans may be arranged such that they are aligned inseries with one another, to ensure that a fan failure does not cause adegenerative airflow path. The positioning of fans in series causes theairflow generated by each fan 904 to be substantially in the samedirection allowing one or more of the fans to provide the same directionof airflow in the event of a fan failure. A spacer 912 may be used tospace a plurality of fans apart to compensate for shock waves such asdescribed above. It is noted that the spacers 912 may be configured toform a seal to one or more fans 904. In this manner, airflow isefficiently directed between fans 904 because the airflow cannot bediverted through openings between a spacer 912 and a fan 904.

In one or more embodiments, the fan assembly 924 may be supported withina support chamber 836 by one or more mounts 908. The fan assembly 924may also be supported by the support chamber 836 or a portion thereof aswell. For example, a portion of the fan assembly 924 may be secured thewall or other portion of a support chamber 836 by one or more fasteners,welds, clips, or the like. In these embodiments, a mount 908 may not berequired.

The one or more mounts 908 may also be configured to form a seal aroundthe fan assembly 924 in some embodiments. For example, one or moremounts 908 may seal a fan assembly 924 to the walls of a support chamber836 in one or more embodiments. As shown in FIG. 9, the mounts 908 forma seal such that air from the inlet 928 must pass through the fanassembly 924 before moving further into the support chamber 836. This isadvantageous in that it prevents unwanted airflows which may reduce thecooling efficiency of the airflow system. For example, without a sealaround the fan assembly 924, air from within the support chamber ratherthan from the inlet 928 may be moved by the fan assembly. This mayreduce the cooling efficiency of the airflow system because heated airmay be recycled rather than exhausted out of an air outlet 932.

The airflow system may also comprise one or more baffles 936 in someembodiments. The baffles 936 may be configured to create turbulence asdesired in the airflow created by the airflow system. As shown in FIG.9, a baffle 936 extends upward from the bottom of the support chamber836 near the outlet 932.

In operation, the airflow system generates airflow to cool parts of thesupport chamber 836 such as the thermal conductor 916. As shown by thearrows of FIG. 9, the generated airflow flows around and, in some cases,through the thermal conductor 916 allowing the thermal conductor tobetter dissipate heat by pushing heat out of the support chamber's airoutlet 932. It will be understood that other parts in the supportchamber 836 may be cooled by the airflow system. For example, the powersupply 920 may be cooled by the airflow from the airflow system. It isnoted that the arrows indicating airflow are exemplary and that variousother airflows may be provided according to the invention.

FIG. 9 also illustrates how components and capture devices of a node maybe arranged within a component chamber 832. In the embodiment shown, thecapture device is a camera 948 which captures images through a dome 808.The other components 956 may be various devices such as one or moreprocessors and transceivers which make up a node, as described above.For example, the component chamber 832 may have one or more videoprocessors, cellular transceivers, and wireless 802.11 transceiverstherein.

The components 956 may be mounted within a component chamber 832 invarious ways. As shown, the components 956 are attached to cards 948.The cards 948 provide the advantage of allowing cards 948 and theirattached components 956 to be quickly and easily removed and installed.In one embodiment, the cards 948 slide into guides 944 having a channelconfigured to accept the edge of a card. In this manner, cards 948 mayslide into place. Once in place, the cards 948 may be secured by alocking pin 952 or other fastener if desired. In one embodiment, thelocking pin passes through an opening of a guide 944 and a card 948 tosecure the card in place. It is contemplated that the locking pin 952may also secured a card frictionally. In this case, the card itself maynot provide an opening.

The component chamber 832 itself may include one or more fans 904 insome embodiments. The fans 904 may be configured to provide additionalairflow within the component chamber 832 if desired. Generally, thisadditional airflow allows for more efficient temperature regulationwithin the component chamber 832. The fans 904 may be pointed indifferent directions to circulate air within the component chamber 832.In the embodiment of FIG. 9 for example, the fans may be pointed inopposite directions to generate a generally circular airflow within thecomponent chamber as illustrated by the arrows. Of course other airflowsmay be provided according to the invention. It can be seen that theairflow transfers heat to and/or is cooled by the thermal conductor 916as it contacts the thermal conductor. In this manner, the temperaturewithin the component chamber 832 may be controlled.

It is contemplated that the environmental control features of thesupport chamber 836 may be controlled by a control system in one or moreembodiments. For instance, the control system may control operation ofthe fan assembly 924, thermal conductor 916, power supply 920, and otherparts of the support chamber 836.

FIG. 10 illustrates a block diagram of an embodiment of a controlsystem. As shown, the control system comprises a controller 1004 and oneor more sensors 1008. As will be described further below, the sensors1008 may be various devices capable of detecting environmental or otherconditions inside a chamber or enclosure or outside a chamber orenclosure. The controller 1004 may connected, such as by an electrical,optical, or wireless connection, to the sensors 1008. The controller1004 may also be connected to parts of the support chamber 836 as wellto allow the controller to control their operation. As shown in FIG. 10,the controller 1004 is connected to the fans 904 of an airflow systemand a power supply 920 to control their operation. It will be understoodthat the controller 1004 may be connected to airflow systems comprisingdevices other than fans in one or more embodiments.

The controller 1004 may be a microprocessor or other circuit in one ormore embodiments. The controller 1004 may be hardwired to control partsof a support chamber 836 or may execute machine readable code from amemory to do the same. It is contemplated that the controller 1004 mayalso control cooling or other temperature control devices within acomponent chamber as well.

In one embodiment, the controller 1004 receives sensor information fromthe one or more sensors 1008 and controls parts of a support chamber 836accordingly. The controller 1004 may also receive operating informationfrom such parts as well. As used herein, sensor information will referto information generated from a sensor. As used herein, operatinginformation will refer to information regarding the operationalcharacteristics of a part of the support chamber 836. For example,operating information may include the current temperature, voltage, fanspeed, and any error conditions for a part. The controller 1004 willgenerally be configured to ensure that the support chamber's temperatureis within range of equipment specifications prior to applying externalpower. In some embodiments, the controller may directly receive externalpower and not be dependent upon the support's chamber power system tooperate.

The sensors 1008 will generally be configured to detect variousenvironmental conditions and send sensor information comprising the sameto the processor. For example, the sensors 1008 may detect temperature,humidity, and airborne particulate concentration. One or more sensors1008 may be located in various chambers or even outside the enclosure todetect environmental conditions. In addition, sensors 1008 may belocated on or near various components or parts of a node to detect theirtemperature.

Based on the sensor information, the controller 1004 may adjust theoperation of one or more parts of the support chamber 836. For example,the controller 1004 may adjust the speed of the fans 904 in a fanassembly 924, the cooling provided by the thermal conductor 916, or bothto maintain a temperature or temperature range. In one embodiment, thecontroller 1004 may also increase or decrease fan speed, cooling, orboth to maintain a temperature or temperature range inside a componentchamber.

In an embodiment where the thermal conductor 916 comprises a poweredelement, such as a Peltier device, the controller may activate anddeactivate the Peltier based on temperature information within thesupport chamber, the component chamber or both. For instance, if thetemperature of a component chamber or device therein is below a certainthreshold the controller 1004 may deactivate a thermal conductor 916 byturning off or removing power from the thermal conductor. Where thetemperature is above a certain threshold, the controller 1004 mayactivate the thermal conductor 916 by turning on or providing power tothe thermal conductor. Since there is a temperature difference betweenthe outside and inside of a sealed component chamber, the heat given offby the chamber's components ensure components in the sealed chamber willoperate in a predetermined temperature range as balanced by the coolingprovided by a thermal conductor 916, such as a Peltier device.

The controller 1004 may also adjust operation of a power supply 920 inone or more embodiments. For example, the controller 1004 may turn offpower to one or more components or parts where their temperature, asdetermined by one or more sensors 1008, is high enough or low enough todamage or destroy the components or parts. The controller 1004 may alsoturn off one, some, or all the components of an component chamber iftemperatures within the component chamber would damage or destroy thecomponents therein.

The controller 1004 may also respond to operating information from oneor more parts of a support chamber 836. For example, the controller 1004may activate or increase speed of one or more fans 904 in response tooperating information indicating the failure of one or more other fans.This allows the airflow system to continue to operate even though one ormore fans 904 have failed. In the event a fan assembly 924 completelyfails, or insufficient airflow is being provided, the controller 1004may cause the power supply 920 to turn off one or more components of anode to prevent damage. Likewise, the controller may respond tooperating information from the thermal conductor 916. For example, ifthe thermal conductor 916 is not operating normally, the controller 1004may increase the fan speed of one or more fans 904 to compensate. Inaddition, the controller 1004 may increase cooling provided by thethermal conductor 916, such as a thermal conductor including a Peltierdevice, in response to abnormal operation of a fan assembly 924.

The control system may include or be connected to a transceiver 1012 inone or more embodiments to communicate with remote devices. As describedabove, a transceiver may allow wired or wireless communication. Thecontroller 1004 may utilize the transceiver 1012 to communicate statusinformation regarding functional or environmental aspects of the system.For example, the controller 1004 may communicate fan speed(s),temperatures, humidity, error conditions, and other information to aremote device. In this manner, the operation of the control system andthe node itself may be monitored/diagnosed remotely. It is contemplatedthat the controller 1004 may also receive instructions or updates viathe transceiver 1012. For example, firmware, software, or configurationupdates may be received. In addition, instructions such as power on,power off, reset, or reboot instructions may be received.

The control system may also include or be connected to a heating element1016 in one or more embodiments which generates heat to warm a chamber,component, or part therein. For example, a heating element 1016 may beused to warm a support or component chamber or their respectiveparts/components. The heating element 1016 is beneficial especially incold environments to ensure that components or parts of a node are notdamaged or destroyed by cold. In one or more embodiments, the heatingelement 1016 may be used to warm up components or parts of a node priorto turning them on. This prevents damage to the components or partscaused by starting them in a cold or very cold temperature. Once thecomponents or parts are on, they may generate their own heat and theheating element 1016 may be shut off.

Alternatively, the heating element 1016 may remain on to warm thecomponents or parts if necessary. Placement of a heating element 1016may be determined on environmental conditions and operating conditionsof the components or parts. In one or more embodiments, a heatingelement 1016 will be placed next to or in contact with the component orpart to be warmed. The heating element 1016 may be any device, now knownor later developed, configured to generate heat as described herein.Typically, the heating element 1016 will be an electrical heatingelement.

In one embodiment, the controller 1004 may utilize sensor information oroperating information to determine when and a heating element 1016should be activated. The controller 1004 may also control the amount ofheat generated by the heating element 1016. When turning on a node, itis contemplated that the controller 1004 may delay turning on one ormore components or parts until their temperatures are above a certainthreshold. For example, the controller 1004 may prevent power from beingsupplied through the power supply to a component or part if temperaturesare too low. This prevents the components or parts from being damaged.At any time, the controller 1004 may also turn off power from the powersupply if temperatures are too low. Alternatively, or in addition, thecontroller 1004 may activate a heating element 1016 if temperatures aretoo low.

Reliability and availability are key factors in surveillance especiallywhen surveillance is adopted for mission critical aspects of ensuringpublic safety. The enclosure described herein provides a controlledenvironment for a node's components to achieve high reliability, uptime,and availability. This also reduces monetary and other costs associatedwith downtime, repair, or both. In fact, it is specifically contemplatedthat one or more embodiments of the enclosure may include designfeatures or configurations that comply to NEBS (Network EquipmentBuilding Standards) Level 3 standards for reliability. For example, anairflow system having backup fans or the like, as described above, maybe included to comply with NEBS Level 3. Such compliance ensures anextremely high level of equipment sturdiness and disaster-tolerance.

While various embodiments of the invention have been described, it willbe apparent to those of ordinary skill in the art that many moreembodiments and implementations are possible that are within the scopeof this invention. In addition, the various features, elements, andembodiments described herein may be claimed or combined in anycombination or arrangement.

1. An enclosure for a node comprising: a rigid multilayer material; asealed component chamber formed from the multilayer material, the sealedcomponent chamber configured to enclose one or more components of thenode; and a support chamber adjacent the sealed component chamber, thesupport chamber comprising: one or more vents configured to allow thepassage of air; a thermal conductor configured to lower the temperatureof the sealed component chamber; an airflow system configured togenerate at least one airflow from the air; and a power supply.
 2. Theenclosure of claim 1, wherein the sealed component chamber furthercomprises a dome configured to allow a camera to capture images.
 3. Theenclosure of claim 1, wherein the support chamber further comprises oneor more baffles to direct the at least one airflow.
 4. The enclosure ofclaim 1, wherein the airflow system comprises a fan assembly having atleast two fans aligned in series by at least one spacer.
 5. Theenclosure of claim 1, wherein the thermal conductor is a Peltier devicecomprising a cooled portion and a heated portion whereby the cooledportion is in physical contact with the sealed component chamber and theheated portion is cooled by the airflow system.
 6. The enclosure ofclaim 5, wherein at least a portion of the cooled portion is within thesealed component chamber.
 7. The enclosure of claim 1, wherein themultilayer material comprises an aluminum layer, an insulating layer,and a coating layer.
 8. The enclosure of claim 1 further comprising: oneor more heating elements; and a controller configured to activate theone or more heating elements to prevent damage caused by coldtemperatures.
 9. An enclosure for a node comprising: a sealed componentchamber configured to enclose one or more components of the node; and asupport chamber adjacent the sealed component chamber, the supportchamber comprising: an air inflow vent at a first end of the supportchamber; an air outflow vent at a second end of the support chamber; anairflow system adjacent the air inflow vent, the airflow systemconfigured to generate at least one airflow; and a thermal conductorcomprising a Peltier device adjacent the airflow system, a portion ofthe thermal conductor in contact with the sealed component chamber. 10.The enclosure of claim 9, wherein the airflow system is supported withinthe support chamber by one or more mounts, whereby the one or moremounts form an airtight seal around the airflow system within thesupport chamber.
 11. The enclosure of claim 9, wherein the airflowsystem comprises at least two fans aligned in series by at least onespacer.
 12. The enclosure of claim 9, wherein the support chamberfurther comprises a power supply adjacent the thermal conductor.
 13. Theenclosure of claim 9, wherein the support chamber further comprises abaffle adjacent the air outflow vent.
 14. The enclosure of claim 9,wherein the support chamber further comprises a controller configured toturn on the Peltier device at a first temperature threshold and turn offthe Peltier device at a second temperature threshold whereby the firsttemperature threshold is at a higher temperature than the secondtemperature threshold.
 15. A method of protecting components of a nodewithin an enclosure comprising: providing a sealed component chambercomprising a multilayer material to enclose one or more components of anode; providing power to the one or more components with a power supply;transferring heat from the sealed component chamber to an adjacentsupport chamber through a thermal conductor; generating at least oneairflow with a airflow system within the support chamber to cool thethermal conductor, wherein the at least one airflow is generated with afan assembly within the support chamber, the fan assembly comprising atleast two fans aligned in series by at least one spacer; measuring atleast one temperature of the sealed component chamber with a temperaturesensor; activating the thermal conductor to cool the sealed componentchamber if the at least one temperature is above a first temperaturethreshold; and deactivating the thermal conductor if the at least onetemperature is below a second temperature threshold.
 16. The method ofclaim 15 further comprising disabling power to the one or morecomponents if the at least one temperature increases beyond a heatthreshold for the one or more components.
 17. The method of claim 15further comprising activating one or more heating elements if the atleast one temperature is below a cold threshold for the one or morecomponents.
 18. The method of claim 15, wherein the sealed componentchamber comprises a multilayer material comprising a rigid structurallayer, an insulating layer, and a coating layer.
 19. The method of claim15, wherein the thermal conductor comprises a Peltier device.
 20. Themethod of claim 15 further comprising reporting one or more errorconditions of the airflow system via a transceiver.